5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
- Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 1-4: Understanding Process Design

The Menu Process


You use a menu process to permit users to select and run other processes. In a typical application, you begin process definition by designing and specifying the main menu that is presented when a user first enters the application. You then proceed to identify what happens when each of the options on the menu is selected. APPX allows you to define up to 249 options (choices) on each menu. An option may invoke another menu, and the number of 'nested' menu levels that you can specify is unlimited.

When you define a menu (as with each type of process), you first provide some basic information about it, including a unique name. Process names must only be unique within a process-type. For example, you can have both a menu and input process called ORDER ENTRY.

Next, you paint a menu image using the Image Editor and then identify the process associated with each option on the menu. Because APPX supports panning (the ability to move about on a surface that is larger than the terminal's physical screen size), a menu can be any dimension up to 449 rows and 250 columns.

Refer to Menu Processes for detailed specifications on defining menu processes.

Application Design Manual                                         "Powered by Appx Software"

64

©2006 By APPX Software, Inc. All Rights Reserved